Skip to content

Configure Renovate #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 13, 2025 •
edited by sourcery-ai bot
Loading

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

  • .devcontainer/devcontainer.json (devcontainer)
  • .github/workflows/build.yml (github-actions)
  • .github/workflows/dotnet-desktop.yml (github-actions)
  • SampleApp/BackEnd/BackEnd.csproj (nuget)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

What to Expect

It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR was generated by Mend Renovate. View the repository job log.

Summary by Sourcery

Add initial Renovate configuration to enable dependency management and onboarding PR

Chores:

  • Add renovate.json with default Renovate presets to activate onboarding PR
  • Enable dependency dashboard, merge confidence badges, and safe environment variables
  • Configure semantic commit types and ignore patterns for common directories
  • Set up package grouping, curated groupings, crowd-sourced replacements, and workarounds

@sourcery-ai Sourcery AI
Copy link

sourcery-ai bot commented Jun 13, 2025 •
edited
Loading

Reviewer's Guide

This PR introduces a Renovate onboarding configuration by adding a top-level renovate.json file that activates dependency update automation with default presets for grouping, ignore patterns, semantic commits, badges, and dashboards.

File-Level Changes

Change Details Files
Add Renovate onboarding config file
  • Create renovate.json with default settings
  • Explain how to activate or disable Renovate via merge or close
 renovate.json
Configure Renovate behavior presets
  • Enable dependency dashboard creation
  • Show Merge Confidence badges on PRs
  • Expose safe environment variables
 renovate.json
Define dependency grouping and upgrade rules
  • Group known monorepo packages together
  • Apply recommended package groupings
  • Include crowd-sourced replacements and workarounds
 renovate.json
Set commit conventions and ignore patterns
  • Use fix for dependency updates and chore for others
  • Ignore node_modules, bower_components, vendor, and test directories
 renovate.json
Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants